home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Collection of Tools & Utilities
/
Collection of Tools and Utilities.iso
/
tex
/
devnag.zip
/
READ.ME
< prev
Wrap
Text File
|
1991-05-26
|
7KB
|
129 lines
*********************************
* *
* DEVANAGARI FOR TeX *
* VERSION 1.2 *
* INSTALLATION INSTRUCTIONS *
* *
*********************************
* *
* Frans J. Velthuis *
* Computing Center *
* University of Groningen *
* The Netherlands *
* *
*********************************
This package contains software for the printing of the devanagari script
with TeX. The devanagari script is used for a number of languages from
Northern and Central India, such as Hindi and Marathi. It is also the script
used for writing and printing Sanskrit.
The package contains the following files:
* DNMACS.TEX: macro file for TeX.
* DEV.STY: macro file for LaTeX.
* DVNG8.TFM, DVNG9.TFM, DVNG10.TFM: TFM files.
* DEVNAG.EXE, DEVNAG.C: preprocessor (MS-DOS executable plus C-source).
* MISSPAAL.DN: an example file.
* MANUAL.TEX: the User Manual.
* READ.ME: this file.
* PK files for 300dpi black-writing laserprinters.
* DEFS.MF, DNCHARS.MF, DVNG10.MF, DVNG9.MF, DVNG8.MF: Metafont source files.
In order to install the software you have to put the files in the right
directories and rename them (if necessary).
* DNMACS.TEX, DEV.STY, MISSPAAL.DN and MANUAL.TEX must be in the directory
where TeX expects it's input. This is something like C:\TEX\INPUTS on
MS-DOS systems.
* DEVNAG.EXE is the preprocessor executable for MS-DOS systems. It must be
in a directory specified in the PATH environment-variable. Preferably it
should be put in the directory where other executable files are kept, often
called BIN.
If you are using the software on a system other than MS-DOS, then the source,
DEVNAG.C, must be compiled with a C-compiler, after which the executable
must be put in a directory where the system can find it.
The source-code regrettably contains very little commentary (mostly due to
laziness on my part, I'm afraid), but with a little persistence it should
be possible to modify the code if you don't like the behaviour of the
preprocessor. Someone might also see it as a challenge to use the new
features of TeX 3.x, Virtual Fonts and the new Metafont in such a way
that a preprocessor is not necessary any more. Would anyone who accomplishes
this please contact me?
* If you do have a 300dpi black-writing laser-printer then you can use the
included PK and TFM files. The TFM-files have to be put in the directory
where TeX keeps its TFM-files, mostly called C:\TEX\FONTS or something like
that. The organization of the fontfiles (PK-files) varies from installation
to installation. Sometimes all the fontfiles are put together in one large
directory and the different magnifications of a font are distinguished by
their filename extension, as is the case with the fonts in this package.
Instead of in a directory the font files are sometimes put in a library.
This is the way it is done in emTeX. And sometimes there are different
directories for each magnification. These directories have 'names' like
300, 329 etc. The fontfiles within these directories have no extensions or
just the extension 'PK'.
According to which fontfile-organization is used on your system, you have
to copy and rename the fontfiles in the PK300 directory in this package.
* If your printer is not a 300dpi black-writing laser-printer, or if you want
to change the appearance of the font or of some characters in it, or if you
want to add characters (there are ligatures in use which are not represented
in this font) then you have to run Metafont and use the .MF files as input.
(The following is taken from: FAQ about TeX)
METAFONT allows you to create your own fonts. METAFONT, unlike TeX,
requires some customization. Each output device for which you will be
generating fonts needs a mode associated with it. Modes are defined
using the mode_def convention described on page 94 of _The METAFONTbook_.
The person who installed METAFONT on your system should know which
modes are defined.
The usual way to create a font with plain METAFONT is to start
it with the line
\mode=<mode name>; mag=<magnification>; input <font file name>
in response to the * prompt or on the METAFONT command line. If
<mode name> is unknown or omitted, then the mode defaults to proof
mode. If this has happened METAFONT will produce an output file
called <font file name>.2602gf. The <magnification> is a floating
point number or magstep (magsteps are defined in _The METAFONTbook_
and _The TeXbook_). If mag=<magnification> is omitted, then the
default is 1. For example, to generate dvng10 at 12pt for an epson
printer you would type
mf \mode=epson; mag=1.2; input dvng10
If you need a special mode that isn't defined for your Metafont,
you can put its commands in a file (e.g., ln03.mf) and invoke
it on the fly with the \smode command. For example, to create
dvng10.300gf for an LN03 printer, using the file
% This is ln03.mf as of 2/27/90
% mode_def courtesy of John Sauter
proofing:=0;
fontmaking:=1;
tracingtitles:=0;
pixels_per_inch:=300;
blacker:=0.65;
fillin:=-0.1;
o_correction:=.5;
(note the absence of the mode_def and enddef commands), we would type
mf \smode="ln03"; input dvng10
There are Metafont source files for 3 different sizes: 8,9 and 10 point:
DVNG8.MF, DVNG9.MF and DVNG10.MF. All of these three source-files make use
of DEFS.MF and DNCHARS.MF. Just as is the case with DEVNAG.C, there is not
much commentary in these Metafont source-files.
A nice feature of Metafont, the possibility to use macro's, is not used very
much because this is very memory-consuming and caused a premature halt of
Metafont on small systems like PC's.
* The package contains a test file called MISSPAAL.DN. (The first page of
a Hindi short story by Mohan Raakesh). So you can verify that everything was
installed successfully by first running the preprocessor: 'devnag misspaal';
after that running TeX: 'tex misspaal';
and then printing the resulting DVI-file <misspaal.dvi> on your printer.
(It is often convenient to create a command procedure which contains
these three commands.) Also included is a User Manual: MANUAL.TEX.
If the installation was successful, you can print this manual and start
creating devanagari text.